Skip to main content

Synchronous/Asynchronous Processing API Flow

00.integration_guide.mdBased on, when integrating SHIELDEX File neutralization (CDR)Asynchronous/SynchronousOrganizing the processing flow.

  • Asynchronous Flow: Decontamination request → Status inquiry (or Callback) → Download
  • Motivation Flow: Demilitarization request → Download*(SHIELDEX server internally repeats status checks and responds with results upon completion)*

1. Asynchronous Processing Flow (Async)​

Asynchronous flow allows the server to register tasks in a queue andReturn Job ID immediatelyand the integration system downloads the results after checking them later.

2. Synchronization Processing Flow (Sync)​

The synchronous processing flow refers to the case where the SHIELDEX server is configured to operate externally like a "synchronous API."\
The server internally uses the existing asynchronous API(POST /v5/cdr, GET /v5/cdr/{jobID})call to oneselfat the completion pointDecontamination results onlyReturns.\
The caller is included in the results.jobIDtoCall the download API separatelydoes.

3. Precautions During Implementation​

  1. Status Check Interval: Calling the status check too frequently (e.g., immediate consecutive calls in a loop) can cause server load/blocking. (200ms interval recommended)
  2. Download Conditions: Status inquiry result iscode: 0**(success)orcode: 1(Exception/Original Import)**You should request a download only in the case of. (code: 2Blocking is not allowed for download)
  3. Synchronous Processing Timeout: To prevent infinite waiting when configuring the synchronous flow (server-side polling)Maximum Wait TimeandRetry Limitmust be placed.